Foxpath Framework · Pillar 03 of 05

The Process Pillar

How work moves from idea to deployed value. Three intake channels, two gates, three delivery stages, and a feedback loop — the part of the framework that turns ambition into shipped outcomes.

Components 6
Shape Linear pipeline
Ownership AI Transformation Lead
Gates Risk · Score · Stage
Foxpath™
Process · Six Components · One Pipeline From idea to deployed value
1 2 3 4 5 ↺ FOXPATH · PILLAR 03 Process INTAKE TRIAGE DELIVERY LOOP ONE PIPE COMPONENT 01 Three-Channel Intake ENTRY Form, Champion, Exec — three channels, one pipeline. LOW MEDIUM HIGH heavier review lighter review COMPONENT 02 Risk Classification FIRST GATE Every use case tiered before resources are committed. VAL EFF RDY SPC PASS /100 COMPONENT 03 Scoring Gate EVALUATION Value · effort · readiness · specificity before resources are committed. CRAWL WALK RUN gate gate COMPONENT 04 Crawl / Walk / Run DELIVERY Manual assist → AI-assisted → full automation. Earn each step. PILOT vs. baseline COMPONENT 05 Pilot-First Deployment VALIDATION Small scale, measured against baseline before scaling investment. SHIP RUBRIC learnings COMPONENT 06 Feedback Loop LEARNING Post-deployment learnings feed the rubric. Process compounds. ENTRY · TRIAGE GATES · DELIVERY · LEARNING LOOP

Six components, in the order work moves

Reading order: pipeline flow
Component 01 Entry

Three-Channel Intake

What: Use cases enter the pipeline through three channels: an open intake form (any employee), Champion-led discovery sessions (monthly per BU), and top-down exec priorities. All three feed one unified pipeline.

Why: A single intake channel will miss either the obvious wins or the strategic ones. Three channels catch ideas where they live and force them into a common queue.

Open Form Champion Discovery Exec Priority
Component 02 First Gate

Risk Classification

What: Every use case is tiered Low / Medium / High before scoring. The tier determines the approval path: light review for Low, DPO + privacy review for Medium, full governance committee for High.

Why: A one-size-fits-all gate either suffocates low-risk work or rubber-stamps high-risk work. Risk tiering routes each use case through the right depth of review.

Low Medium High
Component 03 Evaluation

Scoring Gate

What: Every use case scored across four dimensions before resources are committed: value, effort, readiness, and specificity. A passing score earns a place in the build queue.

Why: Without a scoring gate, the pipeline fills with whoever is loudest. The rubric makes priority defensible, comparable, and revisable as the org learns.

Value Effort Readiness Specificity
Component 04 Delivery

Crawl / Walk / Run

What: Staged delivery: Crawl = manual workflow with AI assist; Walk = AI-assisted workflows with human-in-the-loop; Run = full automation or agentic systems. Each stage has its own gate; nothing skips ahead.

Why: Premature scaling destroys both ROI and trust. Stage gates make progress earnable, not promised.

Crawl Walk Run
Component 05 Validation

Pilot-First Deployment

What: Every use case is piloted at small scale with a documented baseline before broader rollout. ROI claims are measured against that baseline, not against estimates or vendor decks.

Why: A pilot is the cheapest possible disproof. Scaling unvalidated work is how programs lose the executive room, often permanently.

Baseline Small Scale Measured ROI
Component 06 Learning Loop

Feedback Loop

What: Post-deployment learnings — wins, surprises, failures — are folded back into the scoring rubric and intake criteria. The framework improves with every cycle.

Why: A pipeline that doesn't learn is just a longer queue. The feedback loop is what makes the process compound.

Rubric Updates Intake Updates Compounding

Process ownership

Who runs what

AI Transformation Lead

Owns the pipeline end-to-end. Maintains the rubric and the gates.

AI Champions

Source intake. Run discovery, classify risk, draft initial scores in-BU.

Governance Committee

Reviews Medium/High-tier use cases at the scoring gate. Approves Run-stage moves.

"A pipeline that doesn't gate is a queue. A pipeline that doesn't learn is just a longer queue."
Foxpath · Pillar 03